Great.
So today we will continue in second topic in the advance batch, so please, if you have questions on
previous sessions, if you have any doubts, let us know.
Then we will clear before starting this session anyone has a question.
And any time.
And.
OK, no questions.
Let's start today
Karani, let's start today's session, please.
OK, thank you.
So I am outside today, so you may hear some background, some some some background, some some noise
from the background.
So just ignore that because I'm outside.
I'm not in the house today.
So let me share my screen.
I am over, I'm old enough.
Yes, you are edible.
Everything is OK.
Great, great.
So let's let's move on.
So today I want us to look at this.
OK, so someone was money.
You mentioned that there are this some team that wanted to know how to use GitHub.
GitHub.
This is no number 18.
So I wanted to know I wanted to know exactly how use case because because GitHub ideally you can you
can manage GitHub in two is in your opinion.
There is one where you you may be needing to manage the whole software that you are creating that is
including your next the other one, which ideally doesn't make a lot of sense.
Number two is you manage the apps that you are creating and you let your next manager they have created.
OK.
Actually, it makes sense to make to to to speed up this topic since Muhammad Ali Aboubacar from and
his team here in Tunisia, they need to work to cooperate or to start working as a team in the same
for the same application.
You can add more details.
Muhammad Ali, Boubacar
aboutus.
You're OK.
We will start developing our our solution using therapy.
Next, we will want to know how can we work together to get a.
As a team, you see Karani.
Yeah, so so together, you mean OK, what I can show you here is, yes, Google.
When we will
will, uh, developing the application, we will create a customized DOCTYPE or customized existing
today.
So we we shall be working in the same database.
So how can we I mean, as many as this?
OK, so now, now, so they have used GitHub before because what I would like to understand is whether
we are talking about GitHub or the problem here is using Europeanist with GitHub.
Is it how you use GitHub before as a team?
Of course.
OK, so what you are going to do me open let me open GitHub here is important one number one ERP next
you are going to manage GitHub
font pseudo soon.
Very
soon.
He hasn't
been able to.
So what happens here is you are not you are not going to be managing managing all these things inside
of your app.
What you need to do to start with is your need to manage to manage the apparatus have created.
So if here we come to our library management app and released, let me list everything here already
it is initialized.
So if you try to get in it from this file, this directory of it will tell you that it has only been
initialized.
So what you need to do is to create after you have created, you are on GitHub.
Then next thing you need to do is to just connect, connect you up with your people and then you can
share.
And you can say you can share your report with the US team.
Now, you have mentioned you have mentioned about duct tape.
And one thing that's very important to this, Mohammed, is that us, Karen?
Karani.
Yeah, I'm listening.
Yeah, actually, the request we got it from Mohammed and his team, but overall, we will deliver your
Phoenix instance and custom apps with GitHub.
The point, managing your Phoenix with GitHub as an answer to their request.
And we deliver the point for all for all of us.
We are keen to understand GitHub mechanism, how we will use this.
It is not only to reply these questions, but we will deliver the topics as a topics.
You've got what I mean.
Yeah, yeah, that's it.
Sorry to interrupt and continue.
OK, so let's go to GitHub, GitHub and create a report so I will create a new repository here.
I will call it ERP training and I'll go ahead and public know.
Let me make this a private and I will save it when you save, when you save that.
And there's an echo I don't know from where.
So when you save that, you'll notice that this will give you these commands that you should you should
run so that you can have your food on it, so I can even go ahead and copy this.
There's no harm of trying to initialize this a second time.
So remember, we're in our library management instance, so I will put is so Arrhenius.
So this one as reinitialize our GitHub repository so you can do that.
The second thing you don't need to read me.
If you need to order MFL, you can go ahead and do that.
So I'll go ahead and the copy.
The first commit, so commit, put my, my, my code online, so I'll paste this here and I will go
ahead and push.
So this thing is complaining.
Let me hide this.
Not to be a number of things that have been that have been changed here, we can see that the first
one, the first one is there.
Who's not why?
We have the this are a fire and we also have untracked files here.
So the first thing that we are going to do is to add these things to our to our GitHub local GitHub
repo before we put we committed them online.
So let me create this.
And I do get and so we can just go ahead and add everything.
But if if maybe for some reason you do not you do not want to add everything, you are not going to
do this.
So if I look at now, get us everything here, looks looks green.
And that means everything has been has been added and I can go ahead and run my my get permits, get
permit.
And this one has been pushed online.
So everything has gone.
So I can now not online but on my local local GitHub repo so I can now go ahead and copy the next command.
Which is creating this this branch so I can fix this one here go this one has been done.
Then the next thing is no, this is adding a remote online and this is pointing to the report that we
just created.
So I will copy the next command and put it here and go.
That has been done successfully.
And now the final step is to push our code online to our to our report that is online.
So let's go ahead and do that.
Also listed there and go.
And now this one is pushing.
So this is going to ask me for my user because I do not need to set it up there so I can go ahead and
provide that.
Mine is currently Dekay and I'm going to give my email, my password like that.
And that is pushing that is not pushing my code online.
So that is done.
So if I come to my report online and I reload, I am going to have the code.
It is the code for my visitor code for my for my library management.
Up to every code that we have written.
We have utils, we have everything managed here.
We have our python files.
So everything is here now.
Now, remember, this is our this is our library management app we are tracking.
And the point I was going to take to to tell the team is that.
When you edit, I don't remember editing tapes from the mistakes that most of the people do in the beginning,
this is you come to your doctor.
For instance, this one give an example, and then you come here and start customizing things from here.
If you do this.
Yes, this is going to create a python.
I mean, not just one player.
And you can push this you can push this JSON file online to track it on GitHub.
But the most the best way to do this, this customizations, is to go to the customize.
Customize.
Customized, not that customized customized form.
This is where you are going to be needing to customize all the forms that you need to customize.
So when you customize your forms from here, what is going to happen is that the fans are going to be
written here.
Now, this is to directly answer the question that Mohammed asked the team.
What the rest of the team would be needing to do is ideally what they do every day when the when you
are using GitHub.
So just go to your code and the pool, whatever has been, whatever the rest of the team have done.
So, for instance, you can just do get pool.
When you do get the pool, this thing is going to go ahead in the pool or everything that the rest of
the team have pushed to your repository online, and then when the code has to come here, remember,
we have we have you you need to do it migrates, not get back into my grid.
So that is the code that the rest of the team have done can be reflected into your database.
So if, for instance, you had three or four team members, one of the team members working on this
there is working on one of the team members is working on the article duct tape.
The other one is working on membership.
The other one is working on member.
The other one is working on so many other things that would be working on every time, something once,
just like you use getting all the others off their projects.
Every time you finish something, push it only to get when you push end to end.
And the other thing that you may be needing to do is to manage your repository with the different branches.
So let let let don't put push everything to the main branch that we have created here.
You see, I was the only one branch for now.
So let every team member, for instance, have a branch.
So if you have one person working on articulable, you have a branch for Artecoll Library that is managing
everything to do that, then the next team member may be working on library membership, have a branch
for that, and then maybe have one one one team member who pushes all the code that you have in all
the branches and imagines it to the mean to the main main branch here.
Let me give you an example.
Let me go back home.
I have I have a team here.
You can see the projects that we have here.
And I can if I go, for instance, to see custom of.
The branches that we have here, if I go to to request this one, doesn't have a pull request, if I
go to these branches, you see this one has three branches.
I can view all branches.
There is a future here for export use are all permissions.
So everything about user permissions is managed with this branch.
Everything on this is that one of the team members is called thuggishness.
Everything that the issue is doing, he is using all his code here and then I am the only one who can
mudd's everything that they do into the main branch here.
So you may be needing to do that as well.
On you up so late, every feature you work on be pushed to a specific branch and then have one team
member managing everything from that branch to the other branches that I'm into the main branch of your
application.
I don't know that you have any questions up to that point.
So you did get pulled?
Yes, go ahead, go ahead.
Sorry, but so I up to be patient in the database.
How can we manage working on the same system?
So the database will certainly be.
You are looking at one database, Mohammed.
I am hopeful that you are doing your development locally.
Right.
Is it remote or is it local, the development environment?
Not no, a remote remote is remote.
OK, OK, why are you doing it remotivate, why don't you do it for the local machines?
Because we have a server, we have to push our work, the.
Must it go that way, because my thinking would be my thinking would be you do the development on local
machines, you may have a development Savar years where you push all you code and then that development
server maybe can have you can you can do automated automated scripts and get on GitHub, where every
time you push new code to GitHub, GitHub automatically deploys that code to yourself only because in
my thinking, in my experience tells me that developing on a remote server can have a lot of downsides,
because if one person, maybe, for instance, does something wrong or something that can break the
code, the whole of the rest of the team, we have to wait for that thing to be resolved before you
can move on.
But if, for instance, you move, Mohammod, you are working on your machine.
This in My Me is one of your team members.
He is working on his machine and I and someone else.
If you break your code, you break your machine.
Only if you break his machine, you only break his machine.
Break this over.
OK, I understand your point.
I think the question
then the question is development, ERP next environment, where next you have installed it in your local
machine.
I mean, in your opinion, if it is installed in your laptop is at the beginning, we are urban in our
machine, then we have to it in a remote server, you see.
So not now it is in remote server.
I know while working in a remote server in the future, yes.
So what what what are you seeing Karani now?
He's saying you have to keep IRP next in your local machine, in your laptop.
Then you make a folder in GitHub with your name, then from your local machine, you will pull all codes
from GitHub to your local machine.
So you are your local machine will get all updates from other team members every morning, every morning,
all of you, you will do get pulled.
So in 9:00 morning, all of you, they have the same coach locally as if we're looking like that at
this moment.
At this moment.
So it was supposed to finish you finish your work, your work today.
You have something called you prepare and it is ready for the press.
You will do push get pushed.
You will move it to get folder in your branch, in your branch.
OK, yes, guess so, and yeah, go ahead, you.
When we create a GitHub repository, I think we we have we are able to push only our application, not
the whole of the ERP.
There's no point of pushing the whole of Europe because Europe needs to keep updating and you may be
needing to keep updating your instance also there isn't could just track the application you have created.
So let me let me let me let me let me emphasize this point here so that you get.
The first thing you're going to do is create a report on GitHub, then push, for instance, you are
the team leader there or whoever is your team leader, do that so that the rest of the team will just
need to pull from what is here to get started.
So on your local machine, what you're going to do, create the apps or the apps that you may be needing,
then you take the code, you take in every app, you push all those apps to GitHub.
When you push those apps to GitHub, the rest of your team members, let's say, for instance, mammies
in your team member Mamey will install Europea next door like we have done before on his local machine.
And then he because we have added him to you, to these repositories, to the repository you have created
on GitHub.
What he will do is that he will pull the code that is on GitHub to his local machines.
So when he does that, he will automatically be tracking all the apps you have on his local machines
as well.
And then as if, for instance, he is working on Article Braly up DOCTYPE.
When something like this is to to to to create something that you need to avoid problems with GitHub.
Everything, something is ready.
Listen, for instance, mummy has created duct tape and he has tested it is working fine.
Don't wait for tomorrow morning, push it to GitHub then as if Mohammed, for instance, Mohammed,
you are working on a library.
Remember, DOCTYPE before you push, you are called whatever you have that you are on your local machine
and it is working every time, even if it is at the middle of the day before you push this thing to
GitHub, make sure you have food, just to be sure that you have the latest food that is on GitHub,
on your local machine.
So run get the pool.
And then when that succeeds, run, get through so that you know, you are going to be pushed to the
GitHub repository.
And then the next day, mummy maybe has detected something on whatever maybe this app has been working
on.
The first thing he does is not get the first thing he does, even if it is, for instance, is the RPM
in the evening, the first thing he will need to do is get the pool to get the code that is on this
repository, on GitHub, onto his local machine, and then he will get the push to push that code online.
So every time someone wants on something and it works on their local machine, the first step is get
the pool and then get the push, get the pool and then get pushed.
And that way you can have the code that is is remote synchronized to your local machines.
I don't know that this career, Mohammed.
But it's clear even when we we we we we change I doctype we will have an hour or an hour to be.
Tony.
When we do some modification and some that we will have our modification in our database or on our code,
it is on your code.
Let's say, for instance, let's say, for instance, you have this DOCTYPE and it was, you know,
and you say this duct tape on your local machine to keep up with the Busia.
If so, in your database is updated, Europeanist will also track these changes on their files, on
our files here.
Then when you push to get Hub, it will push whatever changes are on these files and then money is a
part of your team.
He will go to GitHub and the pool, the.
So when he pulls these things that will come and write a rewrite these files.
Yes.
Somehow some files will have to be changed.
And then when he does that, he will push the code also online and then the next commander will be needing
to run just to be safe for the sake of being extended for up.
It is bent migrate what it to migrate, does it check their files?
And that may be needing to increase this font a little bit.
If you check their files for any changes that are unthreatened in the database and then it saves them
all the changes to your database.
We are using locally and that's it.
And then you can remember you can use all your remote in any instance.
You can write an automated script so that every time someone pushes through this repository, you don't
have to go to to go to the remote, remote and sarva and to get the pool, but also in the remote Savar,
using, as they say, you can do it manually by going to a switching to your remote environment and
then get the pool and then Benchemsi grid.
You can also do that just like anyone will be doing it in their local machines here.
But again, those are things that you can automate GitHub ways of automating those scripts so that every
time there is something that has been posted here, it will take place and deploy that to your remote
server.
So it is up to you and your team to decide whether you want it is being automated or maybe you are team
leader can be doing that.
Maybe at the end of the day.
At the end of the day, it is helpful to see the future Karani because we are really working a lot with
the GitHub one.
No, no, no.
I told you that we have to see the pictures, the model of picture.
Yeah, yeah, yeah.
This one is on the whoops.
Yeah, yeah.
Yes we will.
Working a lot with pictures.
Yeah I understand they are fixed justice.
I think fictious is another topic somewhere.
Can we have it.
We don't have.
Yeah.
OK was talking Mohammed.
I get it.
We will Mummy and I will look into that and then we will see how we can fix that.
Yes.
Because we told us that we will see it in the advanced topic, how we work, how we will work with fixing.
Yeah.
Fixed.
I agree.
Features fixed will come in very handy.
In that case we are.
OK Mummy.
Will we organise that.
OK, thank you.
Sure, we will.
I took notes about the picture I have questioned now.
You said every time before pushing you to pull right.
Get pulled.
So when you get you do get pulled to retrieve the changes from the repository to your local machine.
So after get pulled, you have to do Benchmade migrate before get push or not required.
No, it is not required to do Benchemsi great before get get pushed, because ideally when you get the
pool, you are going to be in some way the code.
That is only if there are any changes that are are on on your local instance, GitHub is going to pull
those things and and update your files.
So bench migrate is ideally for the database.
So you don't need to do that.
The reason why we need to do get pool before we get pushed is to avoid conflicts, because there may
be someone who has seen the file that you have worked on and did not want a conflict to occur online.
If you have a conflict, you are going to need to resolve to to do to know that you had a conflict on
your local machine and therefore the rest of the team can continue without any problems.
So what is going to happen is when you get the pool and maybe you had worked on the same file with some
other team member, you are going to have a conflict locally and then you are going to resolve that
conflict and then get pushed clean food.
That is not going to cause any issues only.
So here, Deadpool will merge implicitly, a merger will happen right, with good.
Yes, yes, yes, yeah, yeah.
You are going to have your fans updated.
Yes.
But if you want to see the the new code which you have imported or in your local machine, you have
to do well, some regret because it is still a file only so that your database like you mean you you
have to install those new codes in your database to see the if you want to test, right.
Yes.
Yeah, um, OK.
Yeah, good, so can we.
OK, do we have any other question?
Is there anything else that we need to do on GitHub?
You know, any anyone else with suspicion before you can move on to the next topic?
Yes, maybe a small question on the are you always using a get comment line or you have some Refco?
Personally, I do.
I do.
I normally use the command line here, but I have some other people on my team that use this.
I blame not to things, but this could bring this one here.
Is it somewhere.
There is somewhere that we have this one.
We have GitHub.
So you can track that.
You can do everything.
Also on this note, I mean, this this tool here.
OK, good.
Thank you.
OK.
What famous mistake, we should avoid working with it.
We have conflicts, conflicts, pushing, pushing code before you pull.
What happens if maybe someone has done something and then you go and push some?
Some sometimes you can override someone's code and you find that maybe some some features that you thought
you had complete that you had worked on completely.
When you come to, you find that those things are not done and you do realize that it is because someone
get pushed before they pulled what was already done and closed only.
So it is very, very critical to always as a team get pulled before you can push what you have done
only.
So if I understand very well, so before doing a custom app or for any new custom app, I have to create
a separate folder or repository for that customer.
Right.
Well, and get
in and get.
Yes, yes, yes, you have to create a new repository for every app.
Yes.
And under that repository I have many branches, so I have main branch and different branches.
Yes.
Every feature you are working on, the idea is create a branch for it so that you can track it changes
on that branch.
The other reason is the other reason is you don't want to be pushing everything on the main branch,
have a separate branch so that in case you have a problem, you can roll back just one branch instead
of having an issue on the Letterman branch manager code that is tried and tested.
OK, now suppose a new team member joined.
OK, you have to join in in the middle.
OK, so now he will install ERP next in his machine.
Then he will do get to pull, right.
Correct.
He will do get all and get merged and not get merged.
Events migrate.
Correct.
Absolutely correct.
So we do benchmark right now.
He will start at the same level as the other teams.
Correct.
Very.
Once he finish.
Suppose you create for his features a new branch.
He will create a new branch locally.
Then he will do get to push.
So this could enter his local branch.
It will be transferred to get in his branch also.
So when he when he do get the get push automatically, a new branch get created in the repository,
right?
Yes.
When you have changes, what you're going to do here when you are pushing is that you're going to check
out a new branch to get checked out and you are brines and then you are going to put it out online.
What was I going to do is that is going to have a branch here created automatic for you automatically,
because ideally what happens is that GitHub would be managing those things locally.
If you look at these files, the ones we have here.
If I do LSP, we have gates.
So this gate is tracking everything, including our branches.
So when you check out a new branch, it is created inside.
It is.
And now everything we we get pushed.
It pushes whatever is here.
So this will go online and create a new branch for that.
Great.
So here we do this.
Yes, sir.
So most of the talking about cloning a project, cloning application, existing application, they say.
How can we clone the application for four for a new a new developer or new user?
It's exactly what mommy said, what you are going to do for the developer.
You have to install on your local machine and then the next day, remember, you have you have all your
branches here, all your apps, not branches, all your apps on GitHub.
So just come to the branch and add the team member agility member here.
And then what they are going to do is this.
This is good to close to to to Karoonda, the repository when they clone it is going to go directly
to their to in the apps section, in the app section of your application.
I don't need that in the application of your application here.
And then what we do need to do next, remember all the data, the database tables that are on those
apps are not right on the local instance of the machines.
So they will need to do Benchemsi grid so that they can be updated.
Once they do that, they are going to go there will be at the same level with every other developer
that are on that organization.
Mohammed.
OK, thank you.
You're welcome.
May I have something, Karenni, if you want to add Kloner existing customer, you need to use the what
what he we use to install ERP Nexen Frappé, which is Bensch.
Get up, I believe.
And then you would put the link to your GitHub GitHub repository, right?
Absolutely.
That's that's another way.
That's another way of doing it.
We're doing it more.
Yeah.
So I don't know whether.
Mohammod, you got what Maureen is Issing.
Because let me let you go, that you got what you said.
Do think what what he is saying is, let me show you, if I do if I go to Europe next GitHub.
What we normally do and we're installing a new app is bench new app, for instance, when you are installing,
we normally do bench get up and then we give some link here where we normally give.
Here is the link that is normally we normally give the link that is on this branch.
So we normally get the apps from GitHub repository.
So there is nothing that stops us from doing doing bench get up and then we give the link off our up
here is nothing that stops us from doing that.
So we can do that as well.
Maureen, is that clear?
I know Maureen, but Mohammed.
Yes, I see.
And when we will start an application for a customer or a client, how can we do it on?
OK, will you be installing it on the on this, I suppose?
This.
So that is to mean you have developed your your application, it is finished, and now you need to maybe
sell it to a customer.
Yes, and assuming you are not selling it as a service, you will need to go and maybe install it on
the Asaba.
So what you need to do is Iosava, for instance, is just like another machine that is online.
So the exact same way that your developer did when they came with your local machine is the exact same
way you can do on that Savar that these remote.
OK, I see.
Good to see you.
Thank you.
OK, Kiran, if you don't mind, I am more confortable if you do an example of get push, get pull now.
Now, if you you do development and it is a small thing, you tested locally at your level.
But if you have another big project, OK, you have another instance which is called the test instance
or whatever, there is another instance called for instance or staging and before deploy in production.
So all this I cannot repeat.
Now, if I repeated this, this is the decision.
I cannot do it myself.
So if you write comments in front of us and tell you this is the step one, step two, step three from
the pull to push to deploy in production.
Deploying production is something tricky.
We are you know, when you say deploying production, I'm assuming we have a production sarva so I am
going to maybe I can.
What I can do is we change our file.
For instance, we can come here and change something.
What.
No one, no one is going this.
If we do, if we do not.
I'm used to this.
If we do get status here which is used to check whether maybe you have to see this when you are on your
machine.
This one is telling us that our director is clean.
We don't have any untracked files.
If we come here and change something, even if we are.
Did you take this message to these are skiddy text message.
And we say, if not, this is utils file and you see the fact the color of this one has changed, this
is this is very good.
And also here what Maureen was asking this.
This thing has changed here.
So if you are not comfortable with the command line, you can even push it from here and it will go
online.
So this one really is showing you that this file is untracked and it is also showing us on this line
what exactly has changed.
If I come to my command line here, I can do I can now run this employment status.
And this will be showing me that this this particular file is on trust.
So you see, when we ran this against us initially, what we saw is that our country is clean when we
run it.
Now, after changing this file, it's telling us this file is not structured.
The next thing, if you are amandola in person, is to just get Guitard and then you can give the product
to this file.
So I can just see I want to add library.
So this one has to that's why it is doing this, so I can do library management and spelling of good
first round of it.
Yeah.
So I can do that.
So this is good advice.
And then I enter that one has been added.
Now, if I do, I run the same command again with us.
This is green and that means this one has now been added to our remote, to our local.
The next thing is to get a comet.
It comet will come with a message.
You need to provide a message because every every everything you commit online will have.
You need to explain to the team members what exactly have you done?
What are you pushing on?
Like I can say, this is our test for GitHub, but you're are going to be giving meaningful messages
here.
And the biggest one I would ask me that one final has been added and then anything is just that it is
gone.
Oh, sorry, I need to provide my my username.
What is my password?
OK.
That's it.
So not one has been put online and now let me clear this to create room clear if now I come here and
get status again, this is telling me that my writing is clean.
So everything has been pushed online.
Now, if I come online.
If I come online to my to my repository here and I go, he is not in it was utils.
Yeah.
This one, I will find out the message I put.
I change something here.
Yeah.
This one.
This is what we added.
So this one has been pushed online now.
So any other developer who will be needing to be doing it cool will have this line updated on the machines
as well.
Are you comfortable now?
Yes.
Now.
Now you push to get right?
Yes.
Now I want to deploy this.
This changes into production.
So that is why I said that is that is money that is outside of the scope of this training.
But what you can do, No.
One, the production instance has Iosava so that the sarva treated just like that is when you are doing
it manually treated like any other computer you have when you are local development team.
So S.H. into your server and then get the pool, just go to the to the Tamino and get the pool and then
when to migrate you are done.
Alternatively, first you look to the you log in the production server, Linux user and the production
server.
OK, so you go to the best user and go to the application.
As he said, Maureen, you have to create custom, right?
You have to do all these steps.
If you are moving the custom up from development to production, you have to create this app, install
the app.
All these steps need to be done before.
Right.
It's not part of the steps.
No, it's no good steps, and you are when you have it on GitHub, you don't need to create you don't
need to create an app.
You are just getting it from GitHub and that's it.
And then you install it on your machine.
I mean, on your server.
And that is only so that is only for the first time, the other things, you will be just going online
and then get pool and then Benchemsi.
Great and you are done.
OK, can you open a text file or Excel sheet and tell me the right steps?
There takes time.
OK, takes to find text.
Which one.
Now can I or I can write them on this here.
Yeah.
Right, right in the in there too.
Yeah.
I mean I know I have, I have an exercise to move, to move a custom application or a custom report
or any customization from development to production.
And this task any developer is doing on a daily basis, it is doing maybe every day you have to move
something from development to production.
Right.
So now I am not clear for me what I have to do.
First step.
Next step.
As you said, the first step you have to do get up, get up the first.
That's the only for the first time.
Yeah, yeah, yeah.
This steps.
Can you put it in context?
Can you write it in this shot so anyone knows the steps overall.
So if I say after the session I will do this exercise, I have to complete it alone.
I have to do it.
I can do it.
So that's the first step.
You get the up and then you install.
So this will be based once again, you are saying, get in, get up.
You are in the local machine now or you are in production.
It never, ever bothered him both.
OK?
Yeah, yeah, yeah, so Bensch, yeah, this is this will be your side.
So bench side we have side, then your side, then you need to do is pull up.
Then you are up revenue growth.
It's up.
Yes, those are those are the first two things, if you will, those ones are done when those ones are
done.
This will come with everything.
So now after that, if now you are tracking changes, someone has to go to GitHub as they search into
us over.
The thing is, is is get pool.
And then after you get to the bench, my great bench, not be in my great yeah.
OK, now I have a question.
They get comment, you put you issue bit comment under which further under the application folder,
the other Modula folder or under the bench folders, forget coming and up you go into your apps and
you get into the app that you want to get.
That's where you run.
For instance, you see here we are on our app library management.
This is where you do the bench.
If you come here, they get commands.
If you come here and do something like get pool this, you complain that get is no get depository that
is initialised at that level.
So you need to go into your app and then you get a good pool from there, whatever.
Yeah.
That's why you do it.
So I have also put it out on the chart.
Yes, now in the in the report.
Now, we didn't see four report customs report to create a customs report.
The same steps you have to create customs up or and then you create your report under that.
Report, you mean you to add another repository repository?
No, no, no, no, no.
I mean a new report, a totally new report in application to a report like we did last time.
Print format, right?
Uh huh.
We have customized the print format.
So this customization, how you would move it from development to production.
Is it using the comment or these different?
The reports.
Yes, print format, you remember, we have you.
We did our custom print format.
Yeah.
That that one also will be tracked because it is part of it.
It forms part of the code that we have here.
So when you have it on GitHub and you pull it online and you run prints migrated to come with, it will
come to come with that.
And there is something else that Mohammed does mention.
The fixtures fixtures will come in very handy when you when we are handling the same things that fixtures
are going to do, like even move even the data that you have on your inside of the duct.
So there are some questions that fixtures are going to be answering your money, your picture will plan,
and we will plan this, fix your next topic.
And coming up next, we are going to look at pictures.
Yes.
We'll take a look here.
So here's your question.
You have questions yourself.
Hello, Karen.
Can you please keep on writing comment lines to push to push our words, our culture from local to to
remote repo?
You said I keep writing book and the chat and the chat.
Yes.
It's not the same for similar to to any other project.
There is no specific issue for, uh, for the European external.
I'm not getting your question.
Can you please keep on writing the command lines to push our code from local to remote repo?
Jill, you just write GIMPLE, which is getting good from report to local branch.
Margaret, it's not a good read.
It's not the outcome, though.
It's still many, many others comments to push out of the country from local to the remote.
OK, so they are the same government lines for for any others project projects such.
Yeah.
Of ISP dot net is the same as it is the same year is the same.
So can you continue, he said continue, right?
So you did get pulled.
So you do benchwarmer.
Great.
Now you lose your your your coding, your modification, then you are happy.
You will do get Guitard, right, Karenin?
Come and get it and no, no, no.
Remember these steps forward to get whatever is on GitHub to your production is done.
Get put this one for production, right?
Yeah, we are getting code.
This is an app that is on GitHub.
We are given.
Then we install it on our own, our production in server.
Yeah, that's it.
So these other things, in case now someone has done changes and you need to get it to the production
server which already we are already.
You did this.
Yes.
You now go inside and get full and eventually agreed to synchronize.
So next time you do only get full and regrade, correct.
Excellent.
Now, his question, he want to see in the chat with the get push the sequence of comments you have
to issue when you are pushing code from local machine to GitHub, similarly to what we did in production
code.
And he want to put it in chat.
So that will depend.
That's why I don't want to put it here, because if I come here and do get Pooh's, remember, this
command is pushing this command will push your code to the main branch.
And remember, sometimes sometimes you mean you have branches.
So you may need to specify where are you pushing.
You may need to check out the branch that that that you have been working on before you push your code.
So this is get get this is a wide topic.
That is maybe someone is not comfortable with get the first of many to understand to get this is correct.
Yeah.
So I joined the meeting man.
May be late to join later call today.
So that's why he's not he didn't see this bench the get push.
You can find it in the recording and if you have a question we'll take the next call.
OK, ok.
We have a question.
Yes.
There's a command bench update.
Am I right that this command will issue the get pool and bench me great all.
In one step.
I am not sure.
I'm not sure.
Maureen, you never mentioned it, no, no, actually, we use VentureBeat for Air Phoenix, full air
Phoenix, not for our customer.
Right?
I believe it does all the apps.
It does get full bench Maigret and more steps for all the apps installed.
But from from Frappé Frappé folder, not your folder, not it can be from the bench folder.
It will, it will update all the apps installed in your bench.
That makes sense.
Mommy, mommy, what do you think makes sense?
Because ideally we normally do that one I think is going to be here.
My right bench appears as if if you are on this territory, you are able to access the director of apps.
So I think somehow I have never used it myself, but I think somehow this thing can go into the apps
directory and then look at all the apps you have and then go to get a pool or whatever is pulling and
then migrate eventually agreed to them.
I think so.
I have never used it so we can explore to see what it does.
But initially your apps doesn't know there is no link.
Suppose now you create apps in your local machine so your kid doesn't know about your apps.
So you have to link your local apps with the good stuff, right?
Yeah, yeah, this is assuming this is assuming that I assume you and I are on the same team and I created
an app and posted, you pulled it.
So if you do this or the only instance knows we are to get you in, we have to get to where you go up
from so it again, it can do it OK.
Are you using VentureBeat?
Yes, this is what I'm using it, it's just the update of all all the apps of my Bentley.
Yeah, I think I will explore that.
Thank you so much.
You don't do bench pool, Paul sports.
Nothing good will get pushed.
No.
This bench update that you can issue to the.
Come on, Karen, you will see all the steps that is doing.
And you see some progress while it's doing the update, if you if you want to push good from your local
machine to the gate folders.
Are you using this update again or you have the update is only to bring the the change from the remote,
uh, remote GitHub and then running benchmark rate and running patch and doing all the stuff.
I think it's doing a lot of stuff.
I don't know everything, but.
OK, this is the comment we see in the tutorial, in the documentation, so I just wanted to be sure
it was doing this.
But it is this is I feel it is not you cannot control the game because if you are in production and
you issue a bench update, even your IRP next up will get updated and your therapy up app get updated.
And you don't want this update.
Yes, yes, yes.
Yeah.
You raise money that will actually happen.
Yes, yeah, yeah.
You want to test, for example, if you are in the least.
Well, and now there is 13.
It's very dangerous.
So we have to pick which update you want.
OK, and another question about the pull request with contribution with the AARP, next.
So if you have and you want to contribute back to AARP next, how to do this?
Will come
here.
Yeah, I will come back to you just this question come back to you.
Yes.
Now you have created a new features, awesome, awesome features, which probably will they will be
happy and they will pay you to get merged in their application.
So how to contribute back?
Yeah.
Remember remember Europeanist, this opensource.
So what you need to do is to check out your brand and then you push, you push whatever you have done
on your branch to the repository.
And then what they normally do is that we have to review that.
So before before they take it and get it onto the application, they will have to it has to go through
rigorous testing.
And so what they have to do and get in, get show us and get what to do.
Great.
No, that one is I would say this could be its GitHub stuff.
So check out your your custom brands.
It's a it's a tough topic to get out of it, OK?
It's a great we are talking about get only if GitHub topic.
Yeah.
I don't think it's very difficult, but under under your get the repository you have or you never do
it.
I, I feel that has never contributed.
But we are fenigstein.
Well, I have not done it yet.
I still have plans to do it.
But it is it is as easy as just taking out your custom branch and then proceed to the repository.
That's it.
Then the next steps will be the first two steps.
But I want to see it and get out to the front end.
I can I can do it.
I can show you.
I can.
Do you are we doing it with you.
OK, but I've got to get up.
Get up.
If you check out to create a branch you should use the command.
No.
Yes sir.
I have a question.
For our case, I'm going to work with the mom and dad in the same project.
OK, so how can we handle that?
Look, we do care that we took care of that, right?
Sorry, sorry, Karenni money, we took care of that in the earlier today.
Yeah, I will give him any Uzma.
It's better to review the decision.
Uh, and if you have a question or doubts, come back tomorrow or we'll discuss or we will clarify it
again.
So it's very well discussed or.
OK, so, uh, today we completed this, uh, topic, I think.
And it's still open and you get if you are working during this training and you have a question for
it.
We are open to accept questions related to it.
And it's a large topic.
It's very, very large.
But we took a small part of it, which is very important to cooperate with the other team members.
OK, very good.
Very good.
That's it for today.
So let's see you tomorrow, inshallah.
For the same time for another topic.
Thank you, thank you, thank you, thank you, thank you, Karen.
Good bye, my.